Method and system for controlling functionality of lighting devices from a portable electronic device

ABSTRACT

A system for controlling lighting devices includes a processor in communication with a portable electronic device. The processor is configured to receive geolocation data corresponding to an electronic device, and identify one or more light-enabled facilities that are within a distance range of the electronic device. Each of the light-enabled facilities comprises a controller that is communicatively coupled to one or more lighting devices in a network of lighting devices. The system is further configured to receive a light operation request comprising a selected one of the light-enabled facilities and a scene from the electronic device, and transmit the light operation request to cause the controller to activate at least one lighting device at the selected light-enabled facility according to the scene to the controller at the selected light-enabled facility.

RELATED APPLICATIONS AND CLAIMS OF PRIORITY

This patent application is a continuation of and claims priority to U.S.patent application Ser. No. 16/154,050, filed Oct. 8, 2018, which is acontinuation of U.S. patent application Ser. No. 15/786,274, filed Oct.17, 2017, now U.S. Pat. No. 10,098,201. The disclosures of all suchpriority applications are fully incorporated into this document byreference.

BACKGROUND

This disclosure is related to a method and system for controllingfunctionality of light devices and in particular to a method and systemfor controlling light devices from a portable electronic device.

Modern lighting systems include many features that were not previouslyavailable to facility operators and users. For example, lighting systemsthat include light emitting diode (LED) luminaires or other types ofluminaires may offer features such as: controllable dimming; colorselection and color tuning; adjustment of other characteristics ofemitted light such as color temperature or D_(uv); control of the shapeand/or direction of emitted light beams; and pre-programmed scenes orcustomized scenes that incorporate a set of pre-programmed features.

In facilities such as theaters, concert venues, sports fields andstadiums, and even in commercial buildings, the lighting needs canchange frequently depending on who is using the facility at any giventime. For example, a venue may be used for a convention or businessmeeting during the day and a concert or social event in the evening. Asports field may be used for a football or soccer game at one time ofday and a lacrosse team practice at another time of day. However,lighting systems do not easily adapt to the needs of each user andevent. Instead, lighting systems are typically set in a “fully on” or“fully off” arrangement unless the facility is staffed with technicianswho can manually change the lighting system scenarios in response to newusers' needs.

This disclosure describes methods and systems for controlling thefunctionality of a network of one or more lighting devices.

SUMMARY

A system for controlling one or more lighting devices in a lightingdevice control system includes a processor in communication with aportable electronic device and a memory device. The memory devicecontains programming instructions for a lighting system controlapplication. The system receives geolocation data corresponding to anelectronic device and identifies one or more light-enabled facilitiesthat are within a distance range of the electronic device. Each of thelight-enabled facilities may include a controller that iscommunicatively coupled to one or more lighting devices in a network oflighting devices. The system also receives a light operation requestcomprising a selected one of the light-enabled facilities and a scenefrom the electronic device, and transmit, to the controller at theselected light-enabled facility, the light operation request to causethe controller to activate at least one lighting device at the selectedlight-enabled facility according to the scene.

In certain embodiments, the light operation request may also include aservice time duration, and the light operation request may cause thesystem to maintain the at least one lighting device in an activatedstate according to the scene until occurrence of an expiration event.Optionally, the expiration event may be occurrence of an off-timecorresponding to the at least one lighting device or the selectedlight-enabled facility and/or end of the service time duration. In anembodiment, the light operation request is configured to, when receivedby the controller, cause the controller to initiate or maintain the atleast one lighting device in a first condition at a first time, and thenswitch the at least one lighting device to a second condition when thetime duration expires.

Before transmitting the set of available scenes for the one or morecontrollers to the portable device, the system may receive from theportable electronic device, an identifier associated with one of the oneor more controllers, and may then transmit to the portable electronicdevice a set of available scenes for the controller associated with thereceiver identifier.

In some embodiments, the system may receive an identifier associatedwith the controller from the electronic device, and transmit to theelectronic device a set of available scenes for the controller.

In some embodiments, the system may determine whether the electronicdevice is authorized to cause the controller to implement the lightoperation request by receiving a user credential from the electronicdevice or the controller, and verifying the user credential.

Alternatively and/or additionally, the system may determine whether theelectronic device is authorized to cause the controller to implement thelight operation request by receiving a first account identifier from thecontroller associated with the selected scene, receiving a secondaccount identifier from the electronic device, determining usercredentials by comparing the first account identifier with the secondaccount identifier, and verifying the user credential information.

In at least one embodiments, the system may identify one or morelight-enabled facilities by using geolocation data to identify alocation of the electronic device, and accessing a database oflight-enabled facilities and identify, from data in the database, one ormore of the light-enabled facilities having a location that is withinthe distance range of the identified location of the electronic device.

In some embodiments, the system may, before receiving the lightoperation request, retrieve one or more lighting service schedules forthe identified one or more light-enabled facilities, and transmit theone or more lighting service schedules to the electronic device.

In one or more embodiments, the system may use user account informationassociated within the electronic device to authenticate the lightoperation request, and may transmit the light authorization request tothe controller only after authenticating the light operation request.

Optionally, a controller at the selected light-enabled facility may beconfigured to detect whether the electronic device or another devicethat is associated with an account of a user of the electronic device isin proximity of the selected light-enabled facility, and only initiatethe scene at the selected light-enabled facility of the electronicdevice or the other device is in proximity of the selected light-enabledfacility.

In some embodiments, each of the one or more scenes may include a set ofdata corresponding to one or more optical characteristics of one or morelighting devices in the network. The one or more optical characteristicsmay include a brightness or dimming level, color temperature, color,D_(uv), beam shape, and/or beam direction.

In at least one embodiment, before transmitting the set of availablescenes for the one or more controllers to the portable electronicdevice, the system may receive, from at least one of the one or morecontrollers, an indication that the portable electronic device haspaired with the at least one controller.

In some embodiments, the system may also detect geolocation dataindicating a location of the portable electronic device, identify agroup of the light-enabled facilities that are within a distance rangefrom the location of the portable electronic device, transmitidentifying information for the group of the light-enabled facilities tothe portable electronic device, and receive a selection of one of thelocal light-enabled facilities to which to direct the light operationrequest from the portable electronic device. Transmitting the set ofavailable scenes for one or more controllers may include transmittingthe set of available scenes associated with one or more controllers ofthe selected local light-enabled facility. Optionally, the system mayalso include a database of data for a plurality of light-enabledfacilities, and the system may identify the group of light-enabledfacilities that are within a distance range from the portable electronicdevice by accessing the database and extracting identification data forlight-enabled facilities having location data that is within thedistance range of the location of the portable electronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a network of lighting devices, with aproximate mobile electronic device and gateway controller that are usedto control the light emitted by the network of devices.

FIG. 2 illustrates an example of a lighting device that may be used witha network of lighting devices.

FIG. 3 illustrates example steps that a gateway controller may take whenbeing used to control a lighting device.

FIGS. 4a and 4b illustrate example components of a gateway controllerand one or more fixture controllers of a lighting device.

FIG. 5 illustrates example steps that a portable electronic device maytake when being used to control a lighting device.

FIG. 6 illustrates an example of a portable electronic device userinterface that may be used to control the light emitted by one or morelighting devices.

FIG. 7 illustrates example steps that a portable electronic device maytake when being used to control a lighting device.

FIG. 8 illustrates an example user interface by which a user mayschedule lighting service at any of a plurality of facilities in ageographic region.

FIG. 9 illustrates example steps by which a system may control lightingservices at multiple light-enable facilities.

FIG. 10 illustrates various hardware components that may be included inone or more electronic devices.

DETAILED DESCRIPTION

As used in this document, the singular forms “a,” “an,” and “the”include plural references unless the context clearly dictates otherwise.Unless defined otherwise, all technical and scientific terms used hereinhave the same meanings as commonly understood by one of ordinary skillin the art. In this document, when terms such “first” and “second” areused to modify a noun, such use is simply intended to distinguish oneitem from another, and is not intended to require a sequential orderunless specifically stated. As used in this document, the term“comprising” (or “comprises”) means “including (or includes), but notlimited to.”

In this document, the terms “lighting device,” “light fixture,”“luminaire” and “illumination device” are used interchangeably to referto a device that includes a source of optical radiation. Sources ofoptical radiation may include, for example, light emitting diodes(LEDs), light bulbs, ultraviolet light or infrared sources, or othersources of optical radiation. In the embodiments disclosed in thisdocument, the optical radiation emitted by the lighting devices includesvisible light. A lighting device will also include a housing, one ormore electrical components for conveying power from a power supply tothe device's optical radiation source, and optionally control circuitry.

In this document, the terms “communication link” and “communicationpath” mean a wired or wireless path via which a first device sendscommunication signals to and/or receives communication signals from oneor more other devices. Devices are “communicatively connected” if thedevices are able to send and/or receive data via a communication link.“Electronic communication” refers to the transmission of data via one ormore signals between two or more electronic devices, whether through awired or wireless network, and whether directly or indirectly via one ormore intermediary devices.

A “communication interface” of a gateway controller or other electronicdevice is a hardware element configured to enable the device to transmitand/or receive data signals from proximate devices and/or acommunication network. Communication interfaces for communicating withproximate devices may include, for example, a short range wirelesscommunication interface such as a transmitter, a near fieldcommunication (NFC) or radio frequency identifier (RFID) tag, or aBluetooth™ or Bluetooth™ Low Energy (BLE) transceiver. Communicationinterfaces for indirectly communicating with proximate or non-proximatedevices via one or more communication networks may include, for example,a wireless network card with wireless network antenna, a data port, orthe like.

In this document, the terms “controller” and “controller device” mean anelectronic device or system of devices configured to command orotherwise manage the operation of one or more other devices. Forexample, a fixture controller is a controller configured to manage theoperation of one or more light fixtures to which the fixture controlleris communicatively linked. A controller will typically include aprocessing device, and it will also include or have access to a memorydevice that contains programming instructions configured to cause thecontroller's processor to manage operation of the connected device ordevices.

In this document, the terms “memory” and “memory device” each refer to anon-transitory device on which computer-readable data, programminginstructions or both are stored. Except where specifically statedotherwise, the terms “memory” and “memory device” are intended toinclude single-device embodiments, embodiments in which multiple memorydevices together or collectively store a set of data or instructions, aswell as one or more individual sectors within such devices.

In this document, the terms “processor” and “processing device” refer toa hardware component of an electronic device (such as a controller) thatis configured to execute programming instructions. Except wherespecifically stated otherwise, the singular term “processor” or“processing device” is intended to include both single processing deviceembodiments and embodiments in which multiple processing devicestogether or collectively perform a process.

A “computing device” or “electronic device” refers to an electronicdevice having a processor, a memory device, and a communicationinterface for communicating with proximate and/or local devices. Thememory will contain or receive programming instructions that, whenexecuted by the processor, will cause the electronic device to performone or more operations according to the programming instructions.Examples of electronic devices include personal computers, servers,mainframes, virtual machines, containers, gaming systems, televisions,and portable electronic devices such as smartphones, wearable virtualreality devices, Internet-connected wearables such as smart watches andsmart eyewear, personal digital assistants, tablet computers, laptopcomputers, media players and the like. Electronic devices also mayinclude appliances and other devices that can communicate in anInternet-of-things arrangement, such as smart thermostats, homecontroller devices, voice-activated digital home assistants, connectedlight bulbs and other devices. In a client-server arrangement, theclient device and the server are electronic devices, in which the servercontains instructions and/or data that the client device accesses viaone or more communications links in one or more communications networks.In a virtual machine arrangement, a server may be an electronic device,and each virtual machine or container may also be considered to be anelectronic device. In the discussion below, a client device, serverdevice, virtual machine or container may be referred to simply as a“device” for brevity. Additional elements that may be included inelectronic devices will be discussed below in the context of FIG. 8.

FIG. 1 illustrates a lighting system in which any number of lightingdevices 101, 102 are positioned at various locations in an environment,such as a wall, ceiling, mast, tower or other supporting structure in astadium, arena, concert hall, outdoor amphitheater, park or other sportsor entertainment facility, or a commercial building or otherlight-enabled facility. The lighting system also includes a gatewaycontroller 104 communicatively coupled to one or more fixturecontrollers 111, 112 that are connected to one or more lighting devices101, 102. Gateway controller 104 is configured to pair with a portableelectronic device 103, receive a light operation request from theportable electronic device 103 and control at least one lighting device101, 102 via the fixture controller 111, 112 according to the lightoperation request. Each of the gateway controller 104 and portableelectronic device 103 may be capable of communicating with acommunication network 105, such as a cellular communication work, anInternet, a mesh network or other wired or wireless communicationnetworks. The fixture controller 111, 112 includes various components ofan illumination device's control circuitry.

A remote server 106 also may be communicatively connected to thecommunication network 105 so that it can communicate with the portableelectronic device, gateway controller, and/or fixture controllers. Theremote server 106 may include or be connected one or more memory devicesthat collectively store a database 108 of data for multiplelight-enabled facilities, such as scheduling data, data about availablelighting devices and optional functions, available scenes, costs ofvarious services and other data. The portable electronic device 103 mayinclude a memory device containing programming instructions that areconfigured to cause the portable electronic device to perform variousfunctions. In addition, or alternatively, the portable electronic device103 may access the remote server 106 via a communication network 105 toobtain programming instructions that are stored on and received fromand/or executed by the remote server.

Referring to FIG. 2, an example lighting device 101 includes an opticalradiation source, such as any number of lighting modules that includeLEDs, and in various embodiments a number of LED modules sufficient toprovide a high intensity LED device. In various embodiments, a lightingdevice may include multiple types of LED modules. For example, alighting device may include a first type of LED module 203 having LEDsthat are configured to selectably emit white light of various colortemperatures, along with a second type of LED module 205 having LEDsthat are configured to selectably emit light of various colors. Thelighting device 101 may include a housing 201 that holds electricalcomponents such as a fixture controller, a power source, and wiring andcircuitry to supply power and/or control signals to the LED modules. Afixture controller may also be an external device to the lightingdevice.

In FIGS. 4a and 4b , example components of a gateway controller 401 andone or more fixture controllers 431 a, . . . 431 n are shown. In thisdocument, the term “gateway controller” refers to a central controllerdevice that receives commands from a remote electronic device and routesthe commands to appropriate lighting device fixture controllers in anetwork of lighting devices. The gateway controller 401 may include aprocessor 403 and a communications interface that includes a router orswitch 402 with one or more Ethernet ports or optical fiber connectorsconfigured to receive an Ethernet and/or fiber-optic cable. Other typesof cables and connectors may be used, but for purposes of thisdisclosure Ethernet and fiber-optic cables and connectors will be usedas examples.

Each fixture controller 431 n also includes a processor 433 n and, inwired connection embodiments, a switch 432 n having at least two portsthat are each configured to receive an Ethernet or fiber-optic cable.With the ports described above as start and end points, the gatewaycontroller 401 is connected via a communication link 411, such as anEthernet or fiber-optic cable, to form a connection to at least one ofthe fixture controllers 431 a. Alternatively, and/or additionally, thecommunication link 411 may also be a wireless communication link such asa Wi-Fi, a Bluetooth, a NFC network, a mesh network or othercommunication links.

Optionally, each fixture controller may be directly communicativelyconnected to the gateway controller 401. Each fixture controller (e.g.,431 a) may also be similarly connected to at least one other fixturecontroller (e.g., 431 b) via a serial communication link 412, 413 (inthis embodiment, an Ethernet or fiber-optic cable) in a daisy chainconfiguration. In this way, the first fixture controller 431 a in thechain may be connected to the gateway controller 401 and a next fixturecontroller according to a ring topology. The next fixture controller 431b may be connected to the previous fixture controller 431 a and a nextfixture controller in the chain until a final fixture controller 431 nis reached. The final fixture controller 431 n also may be connected tothe gateway controller via a serial communication link 416. In this way,the gateway controller 401 may send commands to each of the lightingdevice's fixture controllers via the various communication links, andthe gateway controller 401 may receive data from each of the lightingdevice's fixture controllers via the various communication links. Insome embodiments, communication may be in a single direction around theloop formed by the devices and communication links; in other embodimentscommunication may be bidirectional in both the clockwise andcounterclockwise directions around the communication links. The ringtopology shown in FIGS. 4a and 4b is optional, and other configurationssuch as a hub-and-spoke configuration (in which the gateway controlleris the hub) or a mesh network may be used.

Any of the lighting device fixture controllers (e.g., 431 n) may beconnected to one or more external devices 451, such as a camera orcomputing device. This connection may be via a wired connection throughan Ethernet or other type of switch 432 n as shown in FIG. 4b , or itmay be a wireless connection via a wireless receiver such as a Wi-Fireceiver 434 n or a short-range communication receiver 435 n such as areceiver configured to receive signals via a Bluetooth™ Low Energy orother communications protocol.

As noted above, the gateway controller 401 also may be communicativelyconnected to the remote server (106 in FIG. 1) and portable electronicdevices (103 in FIG. 1) via one or more communication interfaces tonetworks such as a fiber optic network 441, and/or a wirelesscommunication network such as a local area network, cellular networkand/or the Internet.

Each lighting device will have an associated address, such as anInternet Protocol address. When sending control data to the lightingdevices, the gateway controller may designate the data to be used by alldevices, by a group of the devices, or by individual devices. As eachdevice receives data, its fixture controller may examine the data todetermine whether that data is intended for it. Alternatively, a gatewaycontroller may be configured to be in a “pass-through” mode where itwill forward any received data directly to lighting devices for anyfurther processing. One way in which this may be done is that thegateway controller may associate one or more device addresses with eachset of data. For example, the gateway controller may send a start datasignal, one or more device addresses, and a control data set. If adevice detects (based on the device address that follows the startsignal) that a data set is intended for that device, it may receive andapply that data until the stop command is received. Each device willalso pass the data along to the next interconnected device in thenetwork via the Ethernet or fiber-optic cable.

Optionally, one or more of the lighting devices may add data to the datastream before passing the data stream along to a next device. Forexample, any lighting device's fixture controller 431 b may receive datafrom one or more external or internal sensors, as described above. Thefixture controller may append its device's address to the data stream,so that the data is passed through all lighting devices in the chain andthe fixture controller of the final device 431 n in the chain will passthe data on to the gateway controller 401.

When an external device 451 (such as a camera) is connected to anylighting device's Ethernet switch, the external device also may have anassociated address, and the gateway controller 401 may send data to theexternal device using the external device's address and the wirednetwork described above Similarly, the fixture controller 431 n to whichany external device 451 is attached may send data from the externaldevice to the gateway controller 401 via the data stream just as it maydo with any other data as described above.

Several of the communication links shown in FIGS. 4a and 4b are labeledwith communication protocols that may be used to transmit data acrossthe links. Those labels are by way of example only; other communicationprotocols may be used with any or all of the links shown. In addition,in various embodiments, the gateway controller 401 may includeprogramming configured to translate control data received from a firstprotocol into a second protocol that is compatible with the lightingdevices to which the gateway controller will send commands. In this way,the gateway controller 401 serves as a universal protocol gatewaybetween the lighting devices and one or more external devices orsystems. For example, the gateway controller 401 may translate datareceived from the portable electronic device in a NFC communicationprotocol or other wireless protocol (such as Bluetooth™ Low Energy),whereas the gateway controller 401 may communicate with the remoteserver (106 in FIG. 1) in an Ethernet protocol, and/or it may translatedata received and/or it may translate data received in a fiber channelprotocol, and/or it may translate data that it receives via otherprotocols, into a communication protocol that is compatible with that ofthe illumination devices, such as I²C or that described in the AmericanNational Standards Institute (“ANSI”) “Entertainment Technology—USITTDMX512-A—Asynchronous Serial Digital Data Transmission Standard forControlling Lighting Equipment and Accessories”, which is commonlyreferred to a DMX512 or simply DMX. This document will use the term“DMX” to refer to the DMX512 standard, and its various variations,revisions and replacements, including any future revisions orreplacements that may be consistent with the processes described in thisdisclosure.

Returning to FIG. 1, gateway controller 104 may communicate with aproximate portable electronic device 103 via a direct or indirectcommunication link. The gateway controller 104 may communicate with oneor more fixture controllers 111, 112 or any number of fixturecontrollers, each connecting to one or more lighting devices 101, 102.The gateway controller 104 as well as the proximate portable electronicdevice 103 may communicate with the remote server 106 by any number ofcommunication links. The remote server 106 may be a cloud-based serverthat communicates with the other devices via the communication network105.

FIG. 3 is a flow diagram illustrating a method of controlling one ormore lighting devices in a system such as that disclosed above. Thegateway controller may detect 301 that a portable electronic device onwhich a lighting control application is installed is proximate to thelighting device. Devices are “proximate” to each other if they arewithin a communication range of each other on a local area network orusing a short-range communication or NFC communication protocol.

Short-range communication transceivers are devices that directlycommunicate with each other via relatively short distances on the orderof 100 meters or less, or 10 meters or less. Examples of short-rangetransceivers include those that adhere to short-range communicationprotocols such as ZigBee®, Bluetooth®, and Bluetooth® Low Energy (BLE)transceivers, and/or via infrared (IR) light transceivers. NFCtransceivers are ultra-short range transceivers that adhere to one ormore standards for radio frequency communications that may be used whentwo devices are in close proximity, and may include hardware elementssuch as loop antennas that exchange information via electromagneticinduction. Protocols for implementation of NFC may comply with industrystandards such as ISO/IEC 18092 or ISO/IEC 18000-3, published by theInternational Standards Organization. Typical ranges for near fieldcommunications are approximately 10 cm or less, although it may be 20 cmor less, 4 cm or less, or other ranges. By receiving a connectionrequest via a short-range communication protocol or NFC protocol, thegateway controller will thus detect that the mobile electronic device isproximate to the lighting device.

Detection 301 of proximity may occur, for example, by receiving aconnection request from the portable electronic device via a short-rangecommunication or NFC transceiver. Alternatively, the detection 301 mayoccur by receiving a connection request from the portable electronicdevice via a known wireless local area network (WLAN), such as a Wi-Finetwork that has a limited range and to which the lighting device isalso communicatively connected. By receiving a connection request from amobile electronic device that is communicatively connected to the sameWLAN to which the gateway controller is connected, the gatewaycontroller will thus detect that the mobile electronic device isproximate to the gateway controller.

The gateway controller will also receive, via the communicationinterface, a light operation request 302 from the portable electronicdevice. The communication may occur directly from the portableelectronic device via short-range or NFC communication, or indirectlysuch as via the remote server and one or more networks. The lightoperation request will be one or more data packets that include one ormore settings for one or more optical characteristics of light that theoptical radiation source of the lighting device and/or othercommunicatively connected lighting devices may emit. The one or moreoptical characteristics comprise may include settings such as abrightness or dimming level, color temperature, color, D_(uv), beamshape, and/or beam direction of the light emitted by the opticalradiation source.

The gateway controller may determine whether the portable electronicdevice is authorized to cause the gateway controller to implement thelight operation request 303. If the gateway controller determines thatthe portable electronic device is authorized to initiate the lightoperation request, it will activate one or more lighting devices bycausing the optical radiation source of each lighting device to emitlight that exhibits the one or more optical characteristics of the lightoperation request 304. If the gateway controller determines that theportable electronic device is not authorized to initiate the lightoperation request, it will not implement the request and thus notactivate the optical radiation source according to the request 305.

To determine whether the portable electronic device is authorized tocause the gateway controller to implement the light operation request303, the gateway controller may determine whether the portableelectronic device is associated with a valid unlock token for the lightoperation request. A valid unlock token is a digital identifier that thegateway controller knows represents authorization to activate or changeone or more characteristics of emitted light, such as a code orauthentication token. The gateway controller may receive the unlocktoken from the portable electronic device with the light operationrequest and compare the token with a set of locally or remotely storedauthentication tokens to determine whether the received token matches aknown valid token or adheres to a valid token standard. Alternatively,the gateway controller may receive an account identifier for theportable electronic device, transmit the account identifier to a remoteserver so that the remote server can perform the authentication, andreceive the unlock token from the remote server if the remote serverdetermines that the portable electronic device is authorized to initiatethe light operation request. Alternatively, if the light authorizationrequest is sent to the gateway controller from a remote server, theremote server may send the unlock token to the gateway controller.

Upon determining that the portable electronic device is authorized tosubmit the light operation request, the gateway controller may activateone or more lighting devices according to the selected the one or moreoptical characteristics in the light operation request 304. For example,the gateway controller may send command(s) to the one or more lightingdevices to cause each lighting device's optical radiation source to emitlight that exhibits the optical characteristics values of the lightoperation request. The fixture controller associated with each lightingdevice will implement one or more commands to control operation of theoptical radiation source.

Example methods for altering optical characteristics of LED lights aredisclosed in, for example: (i) U.S. Pat. No. 9,188,307 to Casper et al.,titled “High Intensity LED Illumination Device with AutomatedSensor-Based Control”; (ii) U.S. Pat. No. 9,189,996 to Casper et al.,titled “Selectable, Zone-Based Control for High Intensity LEDIllumination System”; (iii) U.S. patent application Ser. No. 15/670,659,filed by Nolan et al. and titled “Lighting Device LED Module withEffects for Color Temperature Tuning and Color Tuning”; and (iv) U.S.patent application Ser. No. 15/670,671, filed by Nolan et al. and titled“Lighting Device LED Module with Effects for Beam Spread Tuning and BeamShaping.” The disclosures of each of these patents and patentapplications are fully incorporated into this document by reference.

The optical characteristics may include a scene, which is a set of datacorresponding to lighting device settings that will yield variousoptical characteristics of the emitted light for a group of networkedlighting devices. For example, a scene may correspond to a type of asport, such as football, soccer, basketball, tennis, table tennis or anyother sports. A scene may also correspond to a type of event, such as adance party, a birthday party, a lecture, a game or a social event. Eachscene may include a set of data corresponding to one or more opticalcharacteristics of at least one of the networked lighting devices. Forexample, a scene for playing football in a football field may includedata that corresponds to full illuminance setting for all of the lightsaround the football field. In another example, a scene for ice skatingin an arena may include data that correspond to certain lights at fullilluminance and certain light at a dimmed level. Alternative scenes forthe arena may include scenes for a basketball game or music concert. Inanother example, a scene for a lecture in a lecture hall may includedata that correspond to a spotlight above the podium at full illuminanceand other lights in the lecture hall at a dimmed level. In another hall,available scenes for a gymnasium may include options for: (i) a gamescene in which all lights in the gym are illuminated at their highestlevel; (ii) a practice scene in which only lights directed to the courtare lighted at a full illuminance level while lights directed tospectator areas are operated at a reduced illuminance level (i.e.,dimmed); and (iii) a half-court scene in which lights directed to afirst half of the court are operated full illuminance while lightsdirected to the second half of the court are operated at a lesserilluminance level. Optionally, a scene may include some setting valueswill change over time. If so, then the scene may include instructionsfor the gateway controller to cause the values of those opticalcharacteristics of the emitted light to change over time according tothe scene.

Optionally, the light operation request may include a time duration. Thetime duration is a data point indicative of a numeric start time, stoptime and/or or a duration for activation of one or more characteristicsof the optical radiation source. If so, then when activating one or morelighting devices according to the selected scene and the time duration,the gateway controller will initiate or maintain the optical radiationsource of the lighting devices in a first condition (such as “on”)according to the selected characteristics at a first time, via thefixture controller associated with each lighting device. Then when atime out condition occurs 306 corresponding to expiration (i.e., the offtime or the end of the duration), the gateway controller will cause thelighting devices to transition to a second operating condition bydeactivating the optical radiation source and/or the selectedcharacteristics 309. Deactivation may include, via the fixturecontroller associated with each lighting device, completely turning thelight off, or returning the light to a default setting that does notinclude all of the selected characteristic values of the light operationrequest. Optionally, the gateway controller may receive an extensionrequest 307 from the mobile electronic device before the time expires.The extension request will include a new (and later) stop time or anextension to the duration. If the gateway controller determines that themobile electronic device is authorized to extend the time of operationaccording to the extension request (using authorization procedures suchas those described above), the gateway controller will continue toactivate the optical radiation source 308 with the requestedcharacteristic values until the extended time expires, at which time thefixture controller will deactivate the light as described above.

Now, with reference to FIG. 5, an example of a diagram of a process inthe portable electronic device and/or other components of the system isfurther explained. A portable electronic device may include a processorand a display having a user interface. The portable electronic devicemay include or have access to a non-transitory computer readable mediumcontaining the programming instructions. The programming instructions,when executed, may cause the processor to: pair (and/or detect that theportable electronic device has paired) with a gateway controller inproximity to the portable electronic device 501; identify one or morescenes 502; cause the user interface to display the one or more scenes503; receive, via the user interface, a user selection of a scene fromthe one or more scenes and a desired time duration 504; generate orotherwise identify a light operation request comprising the selectedscene and the time duration 505; and transmit the light operationrequest to the gateway controller to cause the gateway controller toactivate at least one of the one or more lighting devices according tothe selected scene and the desired time duration 506.

In identifying the one or more scenes 502, in some scenarios, theportable electronic device may receive the scenes from the gatewaycontroller after pairing with the gateway controller. For example, eachgateway controller may store one or more available scenes thatcorrespond to a type of sport or event suitable for the lighting devicesthat are installed at the premises where the gateway controller isinstalled and controlled by the gateway controller. Upon pairing with aproximate gateway controller, a portable electronic device may receivedata about the available scenes from the gateway controller and displaythese scenes on its display for user selection. Alternatively, uponpairing with a gateway controller, the portable electronic device maytransmit an identifier of the gateway controller to a remote server,which may responsively return a set of available scenes for theidentified gateway controller. In another alternative embodiment(explained in more detail below in FIG. 8) the portable electronicdevice may receive, from a remote server, available scenes for multiplegateway controllers located in a geographic area.

As illustrated above, the gateway controller may first determine whetherthe portable electronic device is authorized to initiate the lightoperation request before activating one or more lighting devicesaccording to the selected scene and the time duration. Upon determiningthe light operation request has been authorized, the gateway controllermay transmit a message indicating such authorization to the portableelectronic device. Correspondingly, the portable electronic device maybe configured to receive a message from the gateway controller and causethe user interface to output a confirmation message indicating that thelight operation request has been authorized 507.

To determine whether a light operation request is authorized, in somescenarios, the gateway controller may determine whether the portableelectronic device has provided valid user credential information, suchas user account identification information and/or user password. Theportable electronic device may transmit such user credential informationto the gateway controller, which in turn transmits the same credentialinformation to the remote server for authorization.

Alternatively, the portable electronic device may directly communicatewith the remote server and transmit the user credential to the remoteserver via an encrypted connection, such as the secure sockets layer(SSL) protocol, in which case the remote server may signal to thegateway controller or the remote electronic device that the lightauthorization request is authorized. In addition, the portableelectronic device may also include the account identifier associatedwith the portable electronic device in the user credential data.

If the authorization is given to the gateway controller by the remotesever or portable electronic device, then the gateway controller maywait to receive the authorization before the gateway controller willsend commands to cause any of its networked lighting devices toimplement the light operation request. If the authorization is given tothe portable electronic device controller by the remote sever or thegateway controller, then the portable electronic device may wait toreceive the authorization before it will send the light operationrequest to the gateway device.

In a non-limiting example, a remote server may be configured to receivethe credential data from the portable electronic device, where thecredential data includes the account identifier. When a gatewaycontroller communicates with the remote server to request authorizationof a light operation request from a portable electronic device, thegateway controller transmits data in the light operation request and theaccount identifier associated with the portable electronic device thatinitiated the light operation request. Upon receiving the lightoperation request and account identifier from the gateway controller,the remote server compares the account identifier it received from thegateway controller with the account identifier received from theportable electronic device directly, to determine the corresponding usercredential information associated with the account identifier. Then theremote server uses the user credential information to determine whetherthe light operation request is authorized. Upon determining that thelight operation request is authorized, the remote server may transmit tothe gateway controller a confirmation message indicating that theportable electronic device is authorized to initiate the light operationrequest. Subsequently, the gateway controller may transmit theconfirmation message to the portable electronic device.

Optionally, a light operation request may include a command to operate asingle lighting device, multiple lighting devices, or all lightingdevices in a system that is communicatively connected to the gatewaycontroller. For example, the light operation request may include one ormore settings for one or more optical characteristics of light that afirst lighting device may emit and different settings for opticalcharacteristics of light emitted by a second lighting device. To dothis, the light operation request may include an identifier for eachlighting device to which commands will be directed, such as an addressof the lighting device, or it may include a general command such as“apply the light operation request to all connected lighting devices.”

FIG. 6 illustrates an example portable electronic device 601 with userinterface 602. The user interface 602 may be a touch-sensitive displaydevice. In other embodiments, instead of or in addition to the displaythe user interface may include other user input/output hardware such asa microphone and/or audio speaker, a keyboard or keypad, or another userinterface device. The user interface 602 may include a fixture selector603 via which the user may select one or more lighting devices tocontrol, and a time selector 604 via which a user may enter a timeduration 614 that may include a start time, stop time or duration.(Alternatively, the system may identify a default time duration, whichmay be part of a scene or part of other programming instructions.) Theuser interface 602 also may include any number of lightingcharacteristics selectors 605, 606 via which the user may enter valuesfor one or more user-selectable settings for characteristics of thelight to be emitted by the selected lighting device(s). The system maydisplay various candidate user-selectable settings 615, such as a dataentry field, a list of options or another selector, for characteristicsthat the user is authorized to select. For any settings that are lockedfor the user's account (i.e., not yet unlocked because the user is notyet authorized to implement the settings), the user-selectable settings616 may be displayed in a non-selectable format, such as a shield oroverlay, or in a greyscale or other format that is not actuatable by theuser until the user unlocks the setting. The user interface also mayinclude an actuator 621 via which the user may unlock the setting, suchas a purchasing interface by which a user may purchase access to therelevant feature.

Optionally, the user interface may include a scene selector 607 viawhich the user may select a scene that includes a set of one or morecharacteristics for one or more lights, in which the setting value forat least some of the characteristic(s) will change over time. Theavailable values 617 may include pre-defined scenes, or the system mayprovide a scene creator user interface via which the user may select thesettings, lighting devices and times that will define a new scene oradjust a pre-defined scene.

FIG. 7 illustrates a process that a portable electronic device mayfollow to initiate a light operation request for one or more proximatelighting devices. The portable electronic device may include a userinterface that outputs various candidate optical characteristics for theoptical radiation source 701. For at least some of the candidate opticalcharacteristics, the user interface may also display user-selectablesettings. The system also may output lock / unlock (as discussed in FIG.6) status indicia 702 of whether an account associated with portableelectronic device or its user has unlocked the ability to selectsettings for each characteristic. For example, for characteristics thatare not locked, user-selectable settings may be presented in auser-selectable format, such as a data entry field, list, or otherstructure. Characteristics for which user-selectable settings that arelocked will not be displayed in a user-selectable format, and may bedisplayed in grayscale, in shielded format, or with other indiciashowing that they are locked, or they may not be displayed at all.

For any characteristic that is locked, the user may input (and theportable electronic device may receive via the user interface) an unlockrequest 703 and transmit the unlock request to the gateway controller.If so, the gateway controller may generate and transmit to a remoteserver a command to charge a user's account an amount required to unlockthe setting 705. Upon receiving confirmation from the remote server thatthe account has been charged, the gateway controller may send to theportable electronic device an unlock code, e.g., an unlock token, tounlock 705 the characteristic so that the user can select the value ofthat characteristic's setting. Alternatively, and/or additionally, theportable electronic device may directly send the unlock request to theremote server and receive an unlock code from the remote server.

When the portable electronic device receives, via the user interface, aselection of at least one of the candidate optical characteristics and avalue for an associated setting for each selected optical characteristic711, it will generate a light operation request 712 as data comprisingeach of the one or more selected optical characteristics and itsassociated setting's value and an account identifier. The portableelectronic device will then transmit 713 the light operation request tothe gateway controller via an NFC or short range communication protocol.

FIG. 8 illustrates a user interface 801 that may be used to schedulelighting services at any of a group of lighting-enabled facilities ingeographic region that is proximate to the portable electronic device.Various lighting facilities 803, 805, 811, 812 are represented on themap by location. Alternatively, available lighting facilities may berepresented in a list or other format, optionally with identifyinginformation describing the types of light-enabled locations that areavailable at the facility (e.g., basketball court, hockey rink, baseballfield, soccer/lacrosse field, and the like). Each of the facilitiesshown in the user interface is light-enabled in that it will include agateway controller and lighting devices as previously described in thisdocument.

As shown in the flowchart of FIG. 9, a remote server may use geolocationdata, such as that received from a GPS sensor of the portable electronicdevice or general location knowledge of the cellular network receiver towhich the portable electronic device connects, to identify the locationof the portable electronic device 901. The remote server then accesses adatabase of light-enabled facilities to identify those that are within ageographic distance range from the device's location 902. The databasemay store location data for each facility and identify those facilitieswhose associated location is within the range of the device's location.The range may be a predetermined range (such as a distance from thedevice's location), or the user interface may receive a user-definedrange.

Optionally, database also may include scheduling information about eachfacility. If so, the server may retrieve lighting service schedules foreach facility for a current time, and optionally for one or more futuretime periods from the database 903. The server may transmit datareflecting the lighting service schedules to the portable electronicdevice so that the portable electronic device may display the schedulingdata on its user interface 904. For example, referring back to FIG. 8facilities 803, 805 that are available at the current time may bedisplayed with a first icon and facilities 811, 812 that are in use andnot currently available may be displayed with a second (different) icon.Other visually distinguishable availability indicators such as text,color, or pop-up may be used as well.

Returning to FIG. 9, the server may then receive a light operationrequest 905 that includes a selection of at least one of the displayedlight-enabled facilities, a service time that corresponds to anavailable lighting service schedule, and a scene (which may simply be adefault scene such as “turn all lights on”), and a future time periodfrom the remote electronic device. The remote server may authenticatethe request (using user account information as described in previousembodiments) 906 and transmit the scene initiation request and scheduleto the gateway controller of the selected facility 907. The gatewaycontroller of the selected facility will then operate the lights at thatfacility according to the schedule and scene using procedures such asthat described above in (for example) FIG. 5. Optionally, the gatewaycontroller may only initiate the scene if and after it detects that theportable electronic device, or another portable electronic device thatis associated with the user's account in proximity of the light-enabledfacility. The gateway controller may detect the portable electronicdevice's location by having paired with the portable electronic device(e.g., by short-range or near-filed communication as previouslydiscussed), or by receiving data from the remote server indicating thatthe remote server has received geolocation data from the portableelectronic device indicating that the device is proximate to the gatewaycontroller.

FIG. 10 is a block diagram of hardware that may be included in any ofthe electronic devices described above, such as the gateway controller,the portable electronic device, the fixture controller, the remoteserver or the lighting device. A bus 1000 serves as an informationhighway interconnecting the other illustrated components of thehardware. The bus may be a physical connection between elements of thesystem, or a wired or wireless communication system via which variouselements of the system share data. Processor 1005 is a processing deviceof the system performing calculations and logic operations required toexecute a program. Processor 1005, alone or in conjunction with one ormore of the other elements disclosed in FIG. 10, is an example of aprocessing device, computing device or processor as such terms are usedwithin this disclosure. The processing device may be a physicalprocessing device, a virtual device contained within another processingdevice, or a container included within a processing device. If theelectronic device is a gateway controller, processor 1005 may be acomponent of the gateway controller. If the electronic device is aremote server, processor 1005 may be a component of a server on acloud-computing network. If the electronic device is a lighting device,processor 1005 may be a component of a fixture controller if the fixturecontroller is an internal component of the lighting device, and thedevice would also include a power supply and optical radiation source asdiscussed above.

A memory device 1010 is a hardware element or segment of a hardwareelement on which programming instructions, data, or both may be stored.An optional display interface 1030 may permit information to bedisplayed on the display 1035 in audio, visual, graphic or alphanumericformat. Communication with external devices, such as a printing device,may occur using various communication interfaces 1040, such as acommunication port, antenna, or near-field or short-range transceiver. Acommunication interface 1040 may be communicatively connected to acommunication network, such as the Internet or an intranet.

The hardware may also include a user interface sensor 1045 which allowsfor receipt of data from input devices such as a keyboard or keypad1050, or other input device 1055 such as a mouse, a touchpad, a touchscreen, a remote control, a pointing device, a video input device and/ora microphone. Data also may be received from an image capturing device1020 such as a digital camera or video camera. A positional sensor 1060and/or motion sensor 1070 may be included to detect position andmovement of the device. Examples of motion sensors 1070 includegyroscopes or accelerometers. Examples of positional sensors 1060 suchas a global positioning system (GPS) sensor device that receivesgeolocation data from an external GPS network.

The features and functions described above, as well as alternatives, maybe combined into many other different systems or applications. Variousalternatives, modifications, variations or improvements may be made bythose skilled in the art, each of which is also intended to beencompassed by the disclosed embodiments.

1. A system for controlling one or more lighting devices, the systemcomprising: a processor; and a memory device containing programminginstructions for a lighting system control application that isconfigured to cause the processor to: receive geolocation datacorresponding to an electronic device, identify one or morelight-enabled facilities that are within a distance range of theelectronic device, wherein each of the light-enabled facilitiescomprises a controller that is communicatively coupled to one or morelighting devices in a network of lighting devices, receive, from theelectronic device, a light operation request comprising a selected oneof the light-enabled facilities and a scene, and transmit, to thecontroller at the selected light-enabled facility, the light operationrequest to cause the controller to activate at least one lighting deviceat the selected light-enabled facility according to the scene.
 2. Thesystem of claim 1, wherein: the light operation request furthercomprises a service time duration; and the lighting control applicationfurther comprises additional instructions to cause the processor tomaintain the at least one lighting device in an activated stateaccording to the scene until occurrence of an expiration event.
 3. Thesystem of claim 2, wherein the expiration event comprises at least oneof the following: occurrence of an off-time corresponding to the atleast one lighting device or the selected light-enabled facility; or endof the service time duration.
 4. The system of claim 1, wherein theprogramming instructions to identify one or more light-enabledfacilities comprise instructions to: use the geolocation data toidentify a location of the electronic device; and access a database oflight-enabled facilities and identify, from data in the database, one ormore of the light-enabled facilities having a location that is withinthe distance range of the identified location of the electronic device.5. The system of claim 1, wherein the lighting control applicationfurther comprises additional instructions to cause the processor to,before receiving the light operation request: retrieve one or morelighting service schedules for the identified one or more light-enabledfacilities; and transmit the one or more lighting service schedules tothe electronic device.
 6. The system of claim 1, wherein the lightingcontrol application further comprises additional instructions to causethe processor to: use user account information associated within theelectronic device to authenticate the light operation request; and whentransmitting the light authorization request to the controller, doing soonly after authenticating the light operation request.
 7. The system ofclaim 1, further comprising the controller at the selected light-enabledfacility, wherein the controller is configured to: detect whether theelectronic device or another device that is associated with an accountof a user of the electronic device is in proximity of the selectedlight-enabled facility; and only initiate the scene at the selectedlight-enabled facility of the electronic device or the other device isin proximity of the selected light-enabled facility.
 8. The system ofclaim 1, wherein the light operation request is configured to, whenreceived by the controller, cause the controller to initiate or maintainthe at least one lighting device in a first condition at a first time,and then switch the at least one lighting device to a second conditionwhen the time duration expires.
 9. The system of claim 1, furthercomprising programming instructions for the lighting system controlapplication to cause the processor to: receive from the electronicdevice, an identifier associated with the controller; and transmit tothe electronic device a set of available scenes for the controller. 10.The system of claim 1, further comprising programming instructions forthe lighting system control application to cause the processor todetermine whether the electronic device is authorized to cause thecontroller to implement the light operation request by: receiving a usercredential from the electronic device or the controller; and verifyingthe user credential.
 11. The system of claim 1, further comprisingprogramming instructions for the lighting system control application tocause the processor to determine whether the electronic device isauthorized to cause the controller to implement the light operationrequest by: receiving a first account identifier from the controller;receiving a second account identifier from the electronic device;determining user credentials by comparing the first account identifierwith the second account identifier; and verifying the user credentialinformation.
 12. The system of claim 1, wherein the scene comprises aset of data corresponding to one or more optical characteristics of oneor more lighting devices in the network, wherein the one or more opticalcharacteristics comprise: a brightness or dimming level; colortemperature; color; D_(uv); beam shape; or beam direction.
 13. Thesystem of claim 1, wherein the programming instructions for the lightingsystem control application to cause the processor to receive the lightoperation request comprise programming instructions to: transmit, to theelectronic device, identifying information for the one or more of thelight-enabled facilities; and receive, from the electronic device, aselection of one of the light-enabled facilities to which to direct thelight operation request, transmit, to the electronic device, the set ofavailable scenes associated with one or more controllers of the selectedlocal light-enabled facility.
 14. The system of claim 13, furthercomprising a database of data for a plurality of light-enabledfacilities; and the programming instructions for the lighting systemcontrol application to cause the processor to identify the one or moreof the light-enabled facilities that are within a distance range fromthe electronic device comprise instructions to access the database andextract from the database identification data for light-enabledfacilities having location data that is within the distance range of thelocation of the electronic device.
 15. The system of claim 14, wherein:the database also includes a plurality of lighting service schedules forat least some of the light-enabled facilities in the database; and thememory device further comprises additional programming instructions thatare configured to cause the processor to, for at least some of thelight-enabled facilities in the group: extract lighting serviceschedules from the database, based on the extracted lighting serviceschedules, identify lighting devices in the group having one or moreavailable lighting service schedule times for which the lightingdevices' light-enabled facility has not been reserved, identify aservice time that corresponds to an available lighting service scheduletimes for the selected light-enabled facility, and update the databaseto indicate that the selected light-enabled facility has been reservedfor the selected service time.
 16. The system of claim 15, wherein theprogramming instructions configured to cause the processor to identifythe service time that corresponds to the available lighting serviceschedule times for the selected light-enabled facility compriseinstructions to cause the processor to: transmit the lighting serviceschedules for at least some of the lighting devices in the group to theelectronic device for output by a user interface of the electronicdevice, and receive, from the electronic device, the service time.
 17. Asystem for controlling one or more lighting devices, the methodcomprising, by a processor: receive geolocation data corresponding to anelectronic device; identifying one or more light-enabled facilities thatare within a distance range of the electronic device, wherein each ofthe light-enabled facilities comprises a controller that iscommunicatively coupled to one or more lighting devices in a network oflighting devices, receiving, from the electronic device, a lightoperation request comprising a selected one of the light-enabledfacilities and a scene; and transmitting, to the controller at theselected light-enabled facility, the light operation request to causethe controller to activate at least one lighting device at the selectedlight-enabled facility according to the scene.
 18. The method of claim17, wherein: the light operation request further comprises a servicetime duration; and the method further comprises, by the processor,maintaining the at least one lighting device in an activated stateaccording to the scene until occurrence of an expiration event.
 19. Themethod of claim 18, wherein the expiration event comprises at least oneof the following: occurrence of an off-time corresponding to the atleast one lighting device or the selected light-enabled facility; or endof the service time duration.
 20. The method of claim 17, whereinidentifying the one or more light-enabled facilities comprises: usingthe geolocation data to identify a location of the electronic device;and accessing a database of light-enabled facilities and identify, fromdata in the database, one or more of the light-enabled facilities havinga location that is within the distance range of the identified locationof the electronic device.
 21. The method of claim 17, furthercomprising, before receiving the light operation request: retrieving oneor more lighting service schedules for the identified one or morelight-enabled facilities; and transmitting the one or more lightingservice schedules to the electronic device.
 22. The method of claim 17,further comprising: using user account information associated within theelectronic device to authenticate the light operation request; and whentransmitting the light authorization request to the controller, doing soonly after authenticating the light operation request.
 23. The method ofclaim 17, further comprising, by a controller at the selectedlight-enabled facility: detecting whether the electronic device oranother device that is associated with an account of a user of theelectronic device is in proximity of the selected light-enabledfacility; and only initiating the scene at the selected light-enabledfacility of the electronic device or the other device is in proximity ofthe selected light-enabled facility.
 24. The method of claim 17, furthercomprising: receiving from the electronic device, an identifierassociated with the controller; and transmitting to the electronicdevice a set of available scenes for the controller.
 25. The method ofclaim 17, further comprising determining whether the electronic deviceis authorized to cause the controller to implement the light operationrequest by: receiving a user credential from the electronic device orthe controller; and verifying the user credential.
 26. The method ofclaim 17, further comprising determining whether the electronic deviceis authorized to cause the controller to implement the light operationrequest by: receiving a first account identifier from the controller;receiving a second account identifier from the electronic device;determining user credentials by comparing the first account identifierwith the second account identifier; and verifying the user credentialinformation.
 27. The method of claim 17, wherein receiving the lightoperation request comprises: transmitting, to the electronic device,identifying information for the one or more of the light-enabledfacilities; and receiving, from the electronic device, a selection ofone of the light-enabled facilities to which to direct the lightoperation request, transmitting, to the electronic device, the set ofavailable scenes associated with one or more controllers of the selectedlocal light-enabled facility.
 28. The method of claim 27, furthercomprising identifying one or more of the light-enabled facilities thatare within a distance range from the electronic device by accessing adatabase and extracting from the database identification data forlight-enabled facilities having location data that is within thedistance range of the location of the electronic device, wherein thedatabase comprises data for a plurality of light-enabled facilities 29.The method of claim 28, wherein: the database also includes a pluralityof lighting service schedules for at least some of the light-enabledfacilities in the database; and the method further comprises, for atleast some of the light-enabled facilities in the group: extractinglighting service schedules from the database, based on the extractedlighting service schedules, identifying lighting devices in the grouphaving one or more available lighting service schedule times for whichthe lighting devices' light-enabled facility has not been reserved,identifying a service time that corresponds to an available lightingservice schedule times for the selected light-enabled facility, andupdating the database to indicate that the selected light-enabledfacility has been reserved for the selected service time.